Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency nodemailer to v6.9.9 - autoclosed #60

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 6, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nodemailer (source) 6.9.4 -> 6.9.9 age adoption passing confidence

Release Notes

nodemailer/nodemailer (nodemailer)

v6.9.9

Compare Source

Bug Fixes
  • security: Fix issues described in GHSA-9h6g-pr28-7cqp. Do not use eternal matching pattern if only a few occurences are expected (dd8f5e8)
  • tests: Use native node test runner, added code coverage support, removed grunt (#​1604) (be45c1b)

v6.9.8

Compare Source

Bug Fixes
  • punycode: do not use native punycode module (b4d0e0c)

v6.9.7

Compare Source

Bug Fixes
  • customAuth: Do not require user and pass to be set for custom authentication schemes (fixes #​1584) (41d482c)

v6.9.6

Compare Source

Bug Fixes
  • inline: Use 'inline' as the default Content Dispostion value for embedded images (db32c93)
  • tests: Removed Node v12 from test matrix as it is not compatible with the test framework anymore (7fe0a60)

v6.9.5

Compare Source

Bug Fixes
  • license: Updated license year (da4744e)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from 7b24822 to cc25af3 Compare September 8, 2023 02:08
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from cc25af3 to c2a17a5 Compare October 9, 2023 14:02
@renovate renovate bot changed the title fix(deps): update dependency nodemailer to v6.9.5 fix(deps): update dependency nodemailer to v6.9.6 Oct 9, 2023
@renovate renovate bot changed the title fix(deps): update dependency nodemailer to v6.9.6 fix(deps): update dependency nodemailer to v6.9.7 Oct 22, 2023
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from c2a17a5 to 066852f Compare October 22, 2023 13:17
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch 2 times, most recently from bc1fe95 to 6c81661 Compare November 14, 2023 01:41
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from 6c81661 to bdd8afd Compare November 22, 2023 22:55
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from bdd8afd to 2c19948 Compare January 1, 2024 17:13
@renovate renovate bot changed the title fix(deps): update dependency nodemailer to v6.9.7 fix(deps): update dependency nodemailer to v6.9.8 Jan 1, 2024
@renovate renovate bot changed the title fix(deps): update dependency nodemailer to v6.9.8 fix(deps): update dependency nodemailer to v6.9.9 Feb 1, 2024
@renovate renovate bot force-pushed the renovate/nodemailer-6.x branch from 2c19948 to 0533449 Compare February 1, 2024 12:16
@renovate renovate bot changed the title fix(deps): update dependency nodemailer to v6.9.9 fix(deps): update dependency nodemailer to v6.9.9 - autoclosed Feb 1, 2024
@renovate renovate bot closed this Feb 1, 2024
@renovate renovate bot deleted the renovate/nodemailer-6.x branch February 1, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants